System and method for facilitating carrier-specific configuration of a user device based on pre-stored information for multiple carriers

ABSTRACT

In certain embodiments, carrier-specific configuration of a user device may be facilitated based on pre-stored information for multiple carriers. In some embodiments, a user device may store information for limited access (that allows the user device to obtain carrier-specific parameters from carrier networks). During activation, the user device may select one of the carrier networks on which the user device is to be configured to operate. Responsive to the selection, the user device may provide, to a carrier-side computer system on the selected carrier network, a request for limited access to the selected carrier network for configuring the user device, wherein the request comprises the stored access information that allows the user device to obtain carrier-specific parameters via the selected carrier network. Responsive to the limited access being granted, the user device may obtain a configuration package from the carrier-side computer system comprising parameters for configuring the user device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a Continuation Application of U.S. patentapplication Ser. No. 15,895,176, filed Feb. 13, 2018, which is aDivisional Application of U.S. patent application Ser. No. 15/173,528,filed Jun. 3, 2016, now U.S. Pat. No. 9,936,331, the subject matter ofwhich is incorporated herein by reference in entirety.

FIELD OF THE INVENTION

The invention relates to carrier-specific configuration of a user deviceand, more particularly, to carrier-specific configuration of a userdevice based on pre-stored information for multiple carriers.

BACKGROUND OF THE INVENTION

Traditionally, mobile devices, such as smartphones or other mobiledevices, providing telecommunication services (e.g., voice, text, data,etc.) are configured for a single telecommunication carrier. Prior toactivation of a mobile device, for instance, the mobile device may beconfigured for a particular carrier by a manufacturer such that thehardware and software are only compatible with a carrier network of theparticular carrier. Although existing solutions may enable a mobiledevice to be configured during activation of the mobile device, typicalsolutions may require the mobile device to connect with a third-partylocal area network and directly obtain the necessary configurations fromthe third-party local area network in order for the mobile device tocompatibly operate on a selected carrier network.

SUMMARY OF THE INVENTION

Aspects of the invention relate to methods, apparatuses, and/or systemsfor facilitating carrier-specific configuration of a user device. In oneor more embodiments, carrier-specific configuration of a user device maybe facilitated using information pre-stored at the user device, such asinformation pre-stored on the user device during the manufacturingprocessing, prior to delivery of the user device to a carrier, prior todelivery of the user device to a user, etc. As an example, thepre-stored information may comprise information for limited access thatallows the user device to obtain carrier-specific parameters forconfiguring the user device from respective carrier networks,configuration packages comprising sets of carrier-specific parametersfor configuring the user device for respective carrier networks, orother pre-stored information.

In certain embodiments, a user device may store information for limitedaccess that allows the user device to obtain carrier-specific parametersfor configuring the user device from carrier networks of differentcarriers. The limited access information may comprise access informationthat allows the user device to obtain carrier-specific parameters forconfiguring the user device via a carrier network of one carrier, accessinformation that allows the user device to obtain carrier-specificparameters for configuring the user device via a carrier network ofanother carrier, and so on. The user device may select, duringactivation of the user device, one of the carrier networks on which theuser device is to be configured to operate. Responsive to the selectionof the carrier network, the user device may provide, to a carrier-sidecomputer system on the selected carrier network, a request for limitedaccess to the selected carrier network for configuring the user devicefor the selected carrier network. The limited access request comprisesat least some of the stored access information that allows the userdevice to obtain carrier-specific parameters for configuring the userdevice via the selected carrier network. Responsive to the limitedaccess being granted by the carrier-side computer system, the userdevice may obtain, from the carrier-side computer system, aconfiguration package comprising one or more carrier-specific parametersfor configuring the user device for the selected carrier network. Theuser device may cause, based on the obtained configuration package, theuser device to be configured for further access to the selected carriernetwork.

In some embodiments, a user device may store configuration packagescomprising sets of carrier-specific parameters for configuring the userdevice for carrier networks of different carriers. The sets ofcarrier-specific parameters may comprise a set of carrier-specificparameters of one configuration package for configuring the user devicefor a carrier network of one carrier, a set of carrier-specificparameters of another configuration package for configuring the userdevice for a carrier network of another carrier, and so on. The userdevice may select, during activation of the user device, one of thecarrier networks on which the user device is to be configured tooperate. Responsive to the selection of the carrier network, the userdevice may obtain a configuration package of the stored configurationpackages that comprises one or more carrier-specific parameters forconfiguring the user device for the selected carrier network. The userdevice may cause, based on the obtained configuration package, the userdevice to be configured for further access to the selected carriernetwork.

In certain embodiments, a carrier-side computer system may obtain, froma user device during activation of the user device, a request forlimited access to a carrier network of the carrier for configuring theuser device for the carrier network. The limited access request maycomprise access information that allows the user device to obtaincarrier-specific parameters for configuring the user device via thecarrier network. The carrier-side computer system may cause, based onthe access information, the limited access to be granted for configuringthe user device. The carrier-side computer system may obtain, from theuser device during the activation of the user device, a configurationrequest comprising at least one of an identifier for the user device oran identifier for a smart card in the user device. Responsive to thelimited access being granted, the carrier-side computer system mayprocess at least one of the identifier of the user device or theidentifier of the smart card to obtain a configuration packagecomprising one or more carrier-specific parameters for configuring theuser device for the carrier network. The carrier-side computer systemmay provide the obtained configuration package to the user device. Theuser device may be configured to operate on the carrier network based onthe carrier-specific parameters of the configuration package.

Various other aspects, features, and advantages of the invention will beapparent through the detailed description of the invention and thedrawings attached hereto. It is also to be understood that both theforegoing general description and the following detailed description areexemplary and not restrictive of the scope of the invention. As used inthe specification and in the claims, the singular forms of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise. In addition, as used in the specification and the claims, theterm “or” means “and/or” unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system for facilitating carrier-specific configuration ofa user device, in accordance with one or more embodiments.

FIG. 2 shows a user device for facilitating carrier-specificconfiguration, in accordance with one or more embodiments.

FIG. 3 shows a flowchart of a method of facilitating carrier-specificconfiguration of a user device based on pre-stored limited accessinformation for multiple carriers, in accordance with one or moreembodiments.

FIG. 4 shows a flowchart of a method of facilitating carrier-specificconfiguration of a user device based on pre-stored configurationpackages for multiple carriers, in accordance with one or moreembodiments.

FIG. 5 shows a flowchart of a method of facilitating configuration of auser device using a configuration package based on user deviceassessment of the configuration package, in accordance with one or moreembodiments.

FIG. 6 shows a flowchart of a method of facilitating carrier-specificconfiguration of a user device based on pre-stored limited accessinformation, in accordance with one or more embodiments.

FIGS. 7A-7C show dataflow diagrams related to facilitatingcarrier-specific configuration of a user device, in accordance with oneor more embodiments.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the embodiments of the invention. It will beappreciated, however, by those having skill in the art that theembodiments of the invention may be practiced without these specificdetails or with an equivalent arrangement. In other instances,well-known structures and devices are shown in block diagram form inorder to avoid unnecessarily obscuring the embodiments of the invention.

FIG. 1 shows a system 100 for facilitating carrier-specificconfiguration of a user device, in accordance with one or moreembodiments. As shown in FIG. 1, system 100 may comprise server 102 (ormultiple servers 102). Server 102 may comprise assessment managementsubsystem 112, activation management subsystem 114, configurationpackage management subsystem 116, notification subsystem 118, or othercomponents.

System 100 may further comprise user device 104 (or multiple userdevices 104 a-104 n). User device 104 may comprise any type of mobileterminal, fixed terminal, or other device. By way of example, userdevice 104 may comprise a desktop computer, a notebook computer, atablet computer, a smartphone, a wearable device, or other user device.Users may, for instance, utilize one or more user devices 104 tointeract with server 102 or other components of system 100. It should benoted that, while one or more operations are described herein as beingperformed by components of server 102, those operations may, in someembodiments, be performed by components of user device 104 or othercomponents of system 100.

As shown in FIG. 2, in an embodiment, user device 104 may comprise anaccess subsystem 202, a configuration subsystem 204, a user devicestorage subsystem 206, a user device presentation subsystem 208, orother components. It should also be noted that, while one or moreoperations are described herein as being performed by components of userdevice 104, those operations may, in some embodiments, be performed bycomponents of server 102 or other components of system 100.

Carrier-Specific Configuration Via a Carrier-Side Computer System

In some embodiments, carrier-specific configuration of a user device maybe facilitated using information pre-stored at the user device, such asinformation pre-stored on the user device during the manufacturingprocessing, prior to delivery of the user device to a carrier, prior todelivery of the user device to a user, etc. As an example, thepre-stored information may comprise information for limited access thatallows the user device to obtain carrier-specific parameters forconfiguring the user device from respective carrier networks (e.g.,cellular networks of respective carriers or other carrier networks),configuration packages comprising sets of carrier-specific parametersfor configuring the user device for respective carrier networks, orother pre-stored information.

In an embodiment, with respect to FIG. 1, access management subsystem112 (of a carrier) may obtain a request for limited access to a carriernetwork of the carrier for configuring a user device (e.g., configuringthe user device for the carrier network). As an example, accessmanagement subsystem 112 may obtain the limited access request from theuser device during activation of the user device or other period. Thelimited access request may comprise access information that allows theuser device to obtain carrier-specific parameters for configuring theuser device via the carrier network. The limited access information (inthe request) may comprise an identifier for the user device, anidentifier for a smart card in the user device, a network identifier(e.g., an Access Point Name (APN) or other identifier) for an accesspoint (on the carrier network) via which the user device can obtainconfiguration information (e.g., a dedicated access point on the carriernetwork for allowing user devices to obtain configuration information orother access point), or other information. Additionally, oralternatively, the limited access information may comprise a username, apassword (also referred to as passphrase, passcode, passkey, etc.), anaccess token, or other information. In an embodiment, the limited accessrequest may be generated at the user device based on pre-storedinformation on the user device, such as the network identifier for theaccess point (on the carrier network for obtaining configurationinformation), a network address associated with such access point, orother pre-stored information (e.g., an identifier associated with theuser device or a user of the user device, an authentication key thatvalidates the associated identifier, etc.). In an embodiment, thepre-stored information on the user device may include an APN that isrecognized by multiple carrier networks of multiple carriers (e.g.,apn.carrierpack.org or other APN) and allows the user device limitedaccess for obtaining carrier-specific parameters via any of the multiplecarrier networks (e.g., T-MOBILE network, VERIZON WIRELESS network, AT&TWIRELESS network, etc.). The limited access request may be generated atthe user device to include the APN recognized by the multiple carriernetworks. In an embodiment, the pre-stored information on the userdevice may include a first APN that is recognized by a first set ofcarrier networks of multiple carriers and allows the user device limitedaccess for obtaining carrier-specific parameters via any of the carriernetworks of the first set, a second APN that is recognized by a secondset of carrier networks of multiple carriers and allows the user devicelimited access for obtaining carrier-specific parameters via any of thecarrier networks of the second set, and so on. The limited accessrequest may be generated at the user device to include one or more ofthe APNs recognized by the respective set of carrier networks.

Responsive to obtaining the limited access request, access managementsubsystem 112 may process the limited access information to verify thatthe user device is authorized for at least limited access (forconfiguring the user device). Upon verification, access managementsubsystem 112 may cause the limited access to be granted for configuringthe user device for the carrier network. As an example, if the limitedaccess request comprises an identifier for the user device and anidentifier for a smart card in the user device, access managementsubsystem 112 may check the user device identifier and the smart cardidentifier against identifiers in carrier access database 132. Ifcorresponding identifiers exist in carrier access database 132 (e.g.,matching user device and smart card identifiers are found), accessmanagement subsystem 112 may grant the limited access for configuringthe user device for the carrier network.

In an embodiment, activation management subsystem 114 may obtain aconfiguration request from the user device (e.g., during the activationof the user device or other period). The configuration request maycomprise an identifier for the user device, an identifier for a smartcard in the user device, information indicating a location associatedwith the user device, or other information. In an embodiment, activationmanagement subsystem 114 may obtain the configuration request from theuser device responsive to limited access (for configuring the userdevice) being granted. In one use case, activation management subsystem114 may process the user device identifier, the smart card identifier,the location information, or other information in the configurationrequest to obtain a configuration package for the user device. Theobtained configuration package may comprise one or more carrier-specificparameters for configuring the user device for the carrier network. Asan example, the carrier-specific parameters may comprise one or moreAPNs (e.g., names of access points, structures that each include anetwork identifier, an operator identifier, etc., or other APNs),network indicator icons, default roaming settings, HTTP and RTSP Proxysettings, boot animations and/or sounds, applications and/or defaultapplication settings, wallpapers, default phone contacts, defaultbrowser homepage, or other carrier-specific parameters.

Configuration package management subsystem 116 may obtain theconfiguration package, and provide the configuration package to the userdevice. Based on the carrier-specific parameters of the configurationpackage, the user device may be configured to operate on the carriernetwork. As an example, responsive to activation management subsystem114 authorizing the user device for configuration (e.g., upon verifyingthe user device identifier, the smart card identifier, or otherinformation in the user device's configuration request), configurationpackage management subsystem 116 may utilize the user device identifierand/or the smart card identifier to obtain the configuration packagefrom configuration database 134. In one use case, for instance, the userdevice identifier may be associated with a particular type of userdevice (e.g., manufacturer, user device model, etc.), and the smart cardidentifier may be associated with one or more supported carriers,locations associated with the user device, etc. Configuration packagesstored in configuration database 134 may each be associated with one ormore types of user device, supported carriers, locations, or otherattributes. In this way, the user device identifier and the smart cardidentifier may be utilized to query configuration database 134 to obtaina configuration package that is also associated with a user device type,a supported carrier, a location, or other attribute associated with theuser device identifier and/or the smart card identifier.

In another use case, where the configuration request comprises alocation associated with user device 104, configuration packagemanagement subsystem 116 may utilize the associated location (e.g., as aparameter of a query to configuration database 134) to obtain theconfiguration package based on the obtained configuration package beingrelated to the associated location. As an example, a user devicepurchased in Baltimore, Md., USA may be pre-loaded with aBaltimore-based newspaper app, while a user device purchased in Seattle,Wash., USA may be pre-loaded with a Seattle-based newspaper app. Assuch, a configuration package associated with the Baltimore location maybe more appropriate for the Baltimore-purchased user device (e.g.,because the Baltimore-associated configuration package may compriseparameters specific to the Baltimore-based newspaper app or otherBaltimore-related application). Additionally, or alternatively, aconfiguration package associated with the Seattle location may be moreappropriate for the Seattle-purchased user device (e.g., because theSeattle-associated configuration package may comprise parametersspecific to the Seattle-based newspaper app or other Seattle-relatedapplication).

Carrier-Specific Configuration at a User Device

In an embodiment, with respect to FIG. 2, user device storage subsystem208 may store information for limited access that allows user device 104to obtain carrier-specific parameters for configuring user device 104from carrier networks of different carriers. In one use case, thelimited access information may be pre-stored on user device 104 by amanufacturer (e.g., during the manufacturing processing, prior todelivery of user device 104 to a carrier, prior to delivery of userdevice 104 to a user, etc.). The limited access information may compriseaccess information that allows user device 104 to obtaincarrier-specific parameters for configuring user device 104 via acarrier network of one carrier, access information that allows userdevice 104 to obtain carrier-specific parameters for configuring userdevice 104 via a carrier network of another carrier, and so on (e.g.,access information that allows user device 104 to obtaincarrier-specific parameters for configuring user device 104 via acarrier network of a third carrier and/or other access information). Inan embodiment, the limited access information may comprise an APN thatis recognized by multiple carrier networks of multiple carriers (e.g.,apn.carrierpack.org or other APN) and allows the user device limitedaccess for obtaining carrier-specific parameters via any of the multiplecarrier networks (e.g., T-MOBILE network, VERIZON WIRELESS network, AT&TWIRELESS network, etc.). In an embodiment, the limited accessinformation may comprise a first APN that is recognized by a first setof carrier networks of multiple carriers and allows the user devicelimited access for obtaining carrier-specific parameters via any of thecarrier networks of the first set, a second APN that is recognized by asecond set of carrier networks of multiple carriers and allows the userdevice limited access for obtaining carrier-specific parameters via anyof the carrier networks of the second set, and so on.

As an example, the limited access information may be pre-stored on aninternal persistent storage of user device 104 other than on a removablesmart card in user device 104 (e.g., SIM card or other smart card). Inthis way, for instance, configuration subsystem 204 may obtain one ormore carrier-specific parameters from a carrier network (for configuringuser device 104 for operation on the carrier network) using the limitedaccess information without necessarily requiring the smart card itselfto include such limited access information. Additionally, oralternatively, different smart cards for different carriers (e.g.,carriers associated with the carrier networks to which the limitedaccess information allows user device 104 have limited access) may beutilized with user device 104 without relying on the utilized smartcard(s) to each store such limited access information.

As another example, the limited access information may be pre-stored ona removable smart card in user device 104. In one use case, forinstance, a smart card may comprise limited access information which,when the smart card is installed in user device 104, allowsconfiguration subsystem 204 to gain limited access to multiple carriernetwork to obtain carrier-specific parameters (for configuring userdevice 104) from those carrier networks.

In an embodiment, configuration subsystem 204 may select one of thecarrier networks on which user device 104 is to be configured tooperate. As an example, configuration subsystem 204 may select one ofthe carrier networks during activation of user device 104 based on userinput indicating the selection, a pre-programmed selection, or otherinput.

In an embodiment, access subsystem 202 may provide, to a carrier-sidecomputer system (e.g., server(s) 102) on a carrier network, a requestfor limited access to the carrier network for configuring user device104 for the carrier network. As an example, access subsystem 202 mayprovide the limited access request to the carrier-side computer systemresponsive to selection of the carrier network (on which thecarrier-side computer system resides) as the carrier network on whichuser device 104 is to be configured to operate. The limited accessrequest may comprise access information (pre-stored at user device 104)that allows user device 104 to obtain carrier-specific parameters forconfiguring user device 104 via the selected carrier network.

In one scenario, limited access information stored at user device 104may allow user device 104 to be configured for access to carriernetworks for the purpose of obtaining configuration information fromthose carrier networks. For example, when one of the carrier networks isselected as the carrier network for which user device 104 is to beconfigured, user device may be specifically configured using the limitedaccess information (e.g., at least a portion thereof that comprise thecarrier-specific parameters for the selected carrier network) to connectand obtain configuration information (e.g., a configuration packagecomprising carrier-specific parameters for configuring user device 104for further access to the selected carrier network) from one or moreaccess points on the selected carrier network. In this way, for example,user device 104 may obtain the configuration package via the selectedcarrier network (e.g., from a carrier-side computer system on thecarrier network) without having to rely on a third-party local areanetwork access point to enable access to the carrier network forconfiguring user device 104.

In a further scenario, the limited access information may comprise anetwork identifier or address (e.g., dedicated for user devices toobtain configuration information), an identifier associated with userdevice 104 or a user thereof (e.g., an identifier of user device 104, anidentifier of a smartcard in user device 104, etc.), an authenticationkey (e.g., that validates the associated identifier), or otherinformation. Access subsystem 202 of user device 104 may utilize thenetwork identifier or address may be utilized to specify the destinationof the limited access request (e.g., to specify an access point on theselected carrier network as the destination). The authentication keystored at user device 104 may correspond to an authentication key storedat a carrier-side database on the selected carrier network, and accesssubsystem 202 may generate the limited access request to include theassociated identifier and provide the limited access request to adestination on the selected carrier network via the stored networkidentifier or address. Upon receipt of the limited access request at thecarrier-side, for example, access management subsystem 112 may utilizedthe associated identifier to look up the corresponding authenticationkey stored at the carrier-side and then cause a randomly generatednumber A to be signed with the corresponding authentication key tocreate a new number B. Access management subsystem 112 may provide therandom number A to user device 104, and access subsystem 204 of userdevice 104 may cause the random number A to be signed with theauthentication key stored at user device 104 to generate a new number Cand relay back the number C. If the number C (generated at user device104) matches the number B (generated at the carrier-side), accessmanagement subsystem 112 may grant the limited access requested by userdevice 104.

In an embodiment, configuration subsystem 204 may obtain, from thecarrier-side computer system, a configuration package comprising one ormore carrier-specific parameters for configuring user device 104 for thecarrier network. As an example, configuration subsystem 204 may obtainthe configuration package from the carrier-side computer systemresponsive to limited access (for configuring user device 104) beinggranted by the carrier-side computer system. Based on the obtainedconfiguration package, configuration subsystem 204 may cause user device104 to be configured for further access to the carrier network. In oneuse case, for instance, configuration subsystem 204 may install theconfiguration package to configure user device 104 with the appropriateAPNs, proxy settings, roaming settings (e.g., default roaming settings),or other carrier-specific parameters for the carrier network.

In an embodiment, where limited access information (which allows userdevice 104 to obtain configuration information from carrier networks) isstored at user device 104, at least some of the limited accessinformation may be deleted from user device 104 after configuring userdevice for a selected carrier network (e.g., during post-configuration“clean-up”). In an embodiment, configuration subsystem 204 may cause atleast part of the limited access information (that allows user device104 to obtain carrier-specific parameters for configuring user device104 via one or more carrier networks other than the selected carriernetwork) to be deleted from user device 104 responsive to configuringuser device 104 for further access to the selected carrier network.Additionally, or alternatively, configuration subsystem 204 may cause atleast part of the limited access information (that allows user device104 to obtain carrier-specific parameters for configuring user device104 via the selected carrier network) to be deleted from user device 104responsive to configuring user device 104 for further access to theselected carrier network.

In an embodiment, user device storage subsystem 206 may storeconfiguration packages comprising sets of carrier-specific parametersfor configuring user device 104 for carrier networks of differentcarriers. In one scenario, the configuration packages may be pre-storedon user device 104 by a manufacturer (e.g., during the manufacturingprocessing, prior to delivery of user device 104 to a carrier, prior todelivery of user device 104 to a user, etc.). The sets ofcarrier-specific parameters may comprise a set of carrier-specificparameters of one configuration package for configuring the user devicefor a carrier network of one carrier, a set of carrier-specificparameters of another configuration package for configuring the userdevice for a carrier network of another carrier, and so on (e.g., a setof carrier-specific parameters of a configuration package forconfiguring user device 104 for a carrier network of a third carrierand/or other set of carrier-specific parameters).

In an embodiment, responsive to selection of a carrier network (e.g.,from a plurality of carrier networks) as the carrier network on whichuser device 104 is to be configured to operate, configuration subsystem204 may obtain, from the configuration packages stored at user device104, a configuration package of the stored configuration packages thatcomprises one or more carrier-specific parameters for configuring theuser device for the selected carrier network. Configuration subsystem204 may then cause user device 104 to be configured for further accessto the selected carrier network based on the obtained configurationpackage. In one use case, for instance, configuration subsystem 204 mayinstall the configuration package to configure user device 104 with theappropriate APNs, proxy settings, roaming settings (e.g., defaultroaming settings), or other carrier-specific parameters for the selectedcarrier network.

As example, the configuration packages may be pre-stored on an internalpersistent storage of user device 104 other than on a removable smartcard in user device 104 (e.g., SIM card or other smart card). In thisway, for instance, configuration subsystem 204 may configure user device104 for operation on one or more carrier networks using the respectivepre-stored configuration packages (e.g., via installation of one of thepre-stored configuration packages) without necessarily requiring thesmart card itself to include such configuration packages. Additionally,or alternatively, different smart cards for different carriers (e.g.,carriers associated with the carrier networks on which user device 104may be configured to operate using the pre-stored configurationpackages) may be utilized with user device 104 without relying on theutilized smart card(s) to each store such configuration packages.

As another example, the configuration packages may be pre-stored on aremovable smart card in user device 104. In one use case, for instance,a smart card may comprise multiple configuration packages which, whenthe smart card is installed in user device 104, allows configurationsubsystem 204 to configure user device 104 for a carrier network (towhich at least one of the pre-stored configuration packages correspond)(e.g., by installing the respective pre-stored configuration package).

In an embodiment, responsive to selection of a carrier network (as thecarrier network on which user device 104 is to be configured tooperate), configuration subsystem 204 may determine whether theconfiguration packages (stored at user device 104) comprises a set ofcarrier-specific parameters for configuring user device 104 for theselected carrier network. As an example, responsive to the storedconfiguration packages comprising a set of carrier-specific parametersfor configuring user device 104 for the selected carrier network,configuration subsystem 204 may obtain the configuration packagecomprising the set of carrier-specific parameters, and install theobtained configuration package on user device 104 to configure userdevice 104 for the selected carrier network.

As another example, however, responsive to the stored configurationpackages not comprising a set of carrier-specific parameters forconfiguring the user device for the selected carrier network,configuration subsystem 204 may attempt to obtain a configurationpackage comprising such a set of carrier-specific parameters from acarrier-side computer system or other source. In one use case, forinstance, if limited access information (that allows user device 104 toobtain carrier-specific parameters for configuring user device 104 viathe selected carrier network) is stored at user device 104, accesssubsystem 202 may utilize the limited access information to generate arequest for the limited access to the selected carrier network to thecarrier-side computer system on the selected carrier network. Responsiveto the limited access being granted, configuration subsystem 204 mayobtain a configuration package comprising one or more carrier-specificparameters (for configuring user device 104 for the selected carriernetwork) from the carrier-side computer system.

In an embodiment, configuration subsystem 204 may provide aconfiguration request to a carrier-side computer system (e.g., of aselected carrier network) during activation of user device 104 or otherperiod. The configuration request may comprise an identifier for theuser device, an identifier for a smart card in the user device,information indicating a location associated with user device, or otherinformation. As an example, where the configuration request comprises alocation associated with user device 104, a configuration packageobtained from the carrier-side computer system may be related to theassociated location. In one use case, for instance, a user devicepurchased in Baltimore, Md., USA may be pre-loaded with aBaltimore-based newspaper app, while a user device purchased in Seattle,Wash., USA may be pre-loaded with a Seattle-based newspaper app. Assuch, a configuration package associated with the Baltimore location maybe more appropriate for the Baltimore-purchased user device (e.g.,because the Baltimore-associated configuration package may compriseparameters specific to the Baltimore-based newspaper app or otherBaltimore-related application). Additionally, or alternatively, aconfiguration package associated with the Seattle location may be moreappropriate for the Seattle-purchased user device (e.g., because theSeattle-associated configuration package may comprise parametersspecific to the Seattle-based newspaper app or other Seattle-relatedapplication).

In an embodiment, a configuration package obtained from a carrier-sidecomputer system may comprise one or more carrier-specific parametersassociated with one location, carrier-specific parameters associatedwith another location, and so on (e.g., carrier-specific parametersassociated with a third location or other carrier-specific parameters).In an embodiment, configuration subsystem 204 may select one or morecarrier-specific parameters (of the obtained configuration package) tobe applied to configure user device 104 based on a location associatedwith user device 104, and cause user device 104 to be configured usingthe selected carrier-specific parameters. As an example, the selectedcarrier-specific parameters may be associated with the location(associated with user device 104).

In an embodiment, a configuration package obtained from a carrier-sidecomputer system may comprise one or more subsets that are supported byuser device 104 and subsets that are not supported by user device 104.In an embodiment, configuration subsystem 204 may select one or moresubsets (of the obtained configuration package) that are supported bythe user device to be used to configure the user device. Responsive tothe selection of the configuration package subsets, configurationsubsystem 204 may cause user device 204 to be configured using theselected configuration package subsets such that subsets of the obtainedconfiguration package that are not supported by the user device are notused to configure the user device.

Examples Flowcharts

FIGS. 3-6 comprise example flowcharts of processing operations ofmethods that enable the various features and functionality of the systemas described in detail above. The processing operations of each methodpresented below are intended to be illustrative and non-limiting. Insome embodiments, for example, the methods may be accomplished with oneor more additional operations not described, and/or without one or moreof the operations discussed. Additionally, the order in which theprocessing operations of the methods are illustrated (and describedbelow) is not intended to be limiting.

In some embodiments, the methods may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The processingdevices may include one or more devices executing some or all of theoperations of the methods in response to instructions storedelectronically on an electronic storage medium. The processing devicesmay include one or more devices configured through hardware, firmware,and/or software to be specifically designed for execution of one or moreof the operations of the methods.

FIG. 3 shows a flowchart of a method 300 of facilitatingcarrier-specific configuration of a user device based on pre-storedlimited access information for multiple carriers, in accordance with oneor more embodiments.

In an operation 302, information for limited access (that allows theuser device to obtain carrier-specific parameters for configuring theuser device from carrier networks of different carriers) may be stored.As an example, the limited access information may comprise accessinformation that allows the user device to obtain carrier-specificparameters for configuring the user device via a carrier network of afirst carrier, access information that allows the user device to obtaincarrier-specific parameters for configuring the user device via acarrier network of a second carrier, and so on. Operation 302 may beperformed by a storage subsystem that is the same as or similar tostorage subsystem 206, in accordance with one or more embodiments.

In an operation 304, one of the carrier networks on which the userdevice is to be configured to operate may be selected during activationof the user device. Operation 304 may be performed by a configurationsubsystem that is the same as or similar to configuration subsystem 204,in accordance with one or more embodiments.

In an operation 306, a request for limited access to the selectedcarrier network (for configuring the user device for the selectedcarrier network) may be provided to a carrier-side computer system onthe selected carrier network. As an example, the limited access requestmay be provided responsive to the selection of the carrier network. Thelimited access request may comprise the stored access information thatallows the user device to obtain carrier-specific parameters forconfiguring the user device via the selected carrier network. Operation306 may be performed by an access subsystem that is the same as orsimilar to access subsystem 202, in accordance with one or moreembodiments.

In an operation 308, responsive to the limited access being granted(e.g., by the carrier-side computer system), a configuration package(comprising one or more carrier-specific parameters for configuring theuser device for the selected carrier network) may be obtained from thecarrier-side computer system. Operation 308 may be performed by anconfiguration subsystem that is the same as or similar to configurationsubsystem 204, in accordance with one or more embodiments.

In an operation 310, the user device may be configured based on theobtained configuration package for further access to the selectedcarrier network. Operation 310 may be performed by an configurationsubsystem that is the same as or similar to configuration subsystem 204,in accordance with one or more embodiments.

FIG. 4 shows a flowchart of a method 400 of facilitatingcarrier-specific configuration of a user device based on pre-storedconfiguration packages for multiple carriers, in accordance with one ormore embodiments.

In an operation 402, configuration packages (comprising sets ofcarrier-specific parameters for configuring the user device for carriernetworks of different carriers) may be stored. As an example, the setsof carrier-specific parameters may comprise a set of carrier-specificparameters of a configuration package for configuring the user devicefor a carrier network of a first carrier, a set of carrier-specificparameters of a configuration package for configuring the user devicefor a carrier network of a second carrier, and so on. Operation 402 maybe performed by a user device storage subsystem that is the same as orsimilar to user device storage subsystem 206, in accordance with one ormore embodiments.

In an operation 404, one of the carrier networks (on which the userdevice is to be configured to operate) may be selected during activationof the user device. Operation 404 may be performed by a configurationsubsystem that is the same as or similar to configuration subsystem 204,in accordance with one or more embodiments.

In an operation 406, a configuration package (of the configurationpackages stored at the user device) comprising one or morecarrier-specific parameters (for configuring the user device for theselected carrier network) may be obtained. Operation 406 may beperformed by a configuration subsystem that is the same as or similar toconfiguration subsystem 204, in accordance with one or more embodiments.

In an operation 408, the user device may be configured based on theobtained configuration package for further access to the selectedcarrier network. Operation 408 may be performed by a configurationsubsystem that is the same as or similar to configuration subsystem 204,in accordance with one or more embodiments.

FIG. 5 shows a flowchart of a method 500 of facilitating configurationof a user device using a configuration package based on user deviceassessment of the configuration package, in accordance with one or moreembodiments.

In an operation 502, a configuration package for configuring a userdevice for a carrier network may be obtained at the user device. Theconfiguration package may, for example, comprise one or morecarrier-specific parameters for configuring the user device for theselected carrier network. As an example, a set of configuration packagesassociated with carrier networks of different carriers may be pre-storedat the user device (e.g., where each configuration package may compriseone or more carrier-specific parameters for configuring the user devicefor a carrier network), and the configuration package may be obtainedfrom the configuration packages pre-stored at the user device responsiveto selection of the carrier network as a carrier network on which theuser device is to operate. As another example, a configuration requestmay be provided from the user device to a carrier-side computer system,a third party computer system (e.g., with respect to the carrier), orother computer system to obtain the configuration package (comprisingthe carrier-specific parameters for configuring the user device for thecarrier network) from the carrier-side computer system, the third partycomputer system, or other computer system. Operation 502 may beperformed by a configuration subsystem that is the same as or similar toconfiguration subsystem 204, in accordance with one or more embodiments.

In an operation 504, subsets of the obtained configuration package (thatare supported by the user device) to be used to configure the userdevice may be selected. Operation 504 may be performed by aconfiguration subsystem that is the same as or similar to configurationsubsystem 204, in accordance with one or more embodiments.

In an operation 506, the user device may be configured using theselected configuration package subsets such that non-supported subsetsof the obtained configuration package are not used to configure the userdevice. Operation 506 may be performed by a configuration subsystem thatis the same as or similar to configuration subsystem 204, in accordancewith one or more embodiments.

FIG. 6 shows a flowchart of a method 600 of facilitatingcarrier-specific configuration of a user device based on pre-storedlimited access information, in accordance with one or more embodiments.

In an operation 602, a request for limited access to a carrier networkof the carrier for configuring the user device for the carrier networkmay be obtained from a user device during activation of the user device.As an example, the limited access request may comprise accessinformation that allows the user device to obtain carrier-specificparameters for configuring the user device via the carrier network.Operation 602 may be performed by an access management subsystem that isthe same as or similar to access management subsystem 112, in accordancewith one or more embodiments.

In an operation 604, the limited access may be caused to be granted (forconfiguring the user device) based on information in the limited accessrequest. As an example, the limited access may be granted to the userdevice responsive to validation of the access information (that allowsthe user device to obtain carrier-specific parameters from the carriernetwork) in the limited access request. Operation 604 may be performedby an access management subsystem that is the same as or similar toaccess management subsystem 112, in accordance with one or moreembodiments.

In an operation 606, a configuration request may be obtained from theuser device during activation of the user device. As an example, theconfiguration request may comprise an identifier for the user device, anidentifier for an smart card in the user device, or other information.Operation 606 may be performed by an activation management subsystemthat is the same as or similar to activation management subsystem 114,in accordance with one or more embodiments.

In an operation 608, information in the configuration request may beprocessed (responsive to the limited access being granted) to obtain aconfiguration package comprising one or more carrier-specific parametersfor configuring the user device for the carrier network. Operation 608may be performed by a configuration package management subsystem that isthe same as or similar to configuration package management subsystem116, in accordance with one or more embodiments.

In an operation 610, the obtained configuration package may be providedto the user device. The user device may be configured to operate on thecarrier network based on the carrier-specific parameters of the providedconfiguration package. Operation 610 may be performed by a configurationpackage management subsystem that is the same as or similar toconfiguration package management subsystem 116, in accordance with oneor more embodiments.

FIGS. 7A-7C comprise example dataflow diagrams related to operationsthat enable the various features and functionality of the system asdescribed in detail above. The related operations presented below areintended to be illustrative and non-limiting. In some embodiments, forexample, one or more additional operations not described may beperformed, and/or one or more of the operations discussed may not beperformed. Additionally, the order in which the related operations areillustrated (and described below) is not intended to be limiting.

FIG. 7A shows a dataflow diagram related to facilitatingcarrier-specific configuration of a user device based on pre-storedlimited access information, in accordance with one or more embodiments.As an example, computer system 702 may be a computer system of aselected carrier network, and user device 704 may be a user device at acustomer premise.

In an embodiment, at 712, limited access information for accessingcomputer systems of multiple carrier networks may be stored at userdevice 704. As an example, in one use case, the stored limited accessinformation may comprise information for limited access that allows theuser device 704 to obtain carrier-specific parameters for configuringthe user device 704 from carrier networks of different carriers. Inanother use case, the limited access information may be pre-stored onuser device 704 by a manufacturer (e.g., during the manufacturingprocessing, prior to delivery of user device 704 to a carrier, prior todelivery of user device 704 to a user, etc.).

At 714, a carrier network (on which user device is to be used) may beselected at user device 704. At 716, responsive to selection of thecarrier network, limited access information for the selected carriernetwork may be obtained by user device 104 from storage.

At 718, a request for limited access for configuration may be generatedat user device 704 and provided to computer system 702. The limitedaccess request may, for example, be generated to comprise the limitedaccess information for the selected carrier network (that was pre-storedand obtained by user device 704 from storage responsive to selection ofthe carrier network).

At 720, responsive to obtaining the limited access request,authorization for user device 704 to have limited access to the selectedcarrier network may be verified at computer system 702.

At 722, if the authorization for user device 704 to have limited accessto the selected carrier network is verified, a notification of thelimited access grant may be generated at computer system 702 andprovided to user device 704.

At 724, a request for activation and/or for a configuration package maybe generated at user device 704 and provided to computer system 702.

At 726, responsive to obtaining the activation/configuration request,authorization for the activation and/or the configuration package may beverified at computer system 702.

At 728 and 730, if the authorization for the activation and/or theconfiguration package is verified, the configuration package may beobtained at computer system 702 and provided to user device 704, anduser device 704 may be activated on the carrier side at computer system702. At 732, responsive to obtaining the configuration package, theconfiguration package may be installed at user device 704. At 734, anotification of the activation on the carrier side may be generated atcomputer system 702 and provided to user device 704.

At 736, post-configuration clean-up may be performed at user device 704.As an example, at least part of the limited access information may becaused to be deleted from user device 704. In one use case, for example,responsive to user device 704 being configured for the selected carriernetwork, (i) the limited access information that allows user device 704to obtain carrier-specific parameters for configuring user device 704via one or more carrier networks other than the selected carriernetwork, (ii) the limited access information that allows user device 704to obtain carrier-specific parameters for configuring user device 704via the selected carrier network, or (iii) both may be deleted. Asanother example, responsive to user device 704 being configured for theselected carrier network, the configuration package obtained fromcomputer system 704 may be deleted.

FIG. 7B shows a dataflow diagram related to facilitatingcarrier-specific configuration of a user device based on pre-storedconfiguration information, in accordance with one or more embodiments.In an embodiment, at 742, configuration packages may be stored at userdevice 704. As an example, the configuration packages may comprise setsof carrier-specific parameters for configuring user device 704 forcarrier networks of different carriers. In one scenario, the sets ofcarrier-specific parameters may comprise a set of carrier-specificparameters of a configuration package for configuring the user devicefor a carrier network of a first carrier, a set of carrier-specificparameters of a configuration package for configuring the user devicefor a carrier network of a second carrier, and so on. In anotherscenario, the configuration packages may be pre-stored on user device704 by a manufacturer (e.g., during the manufacturing processing, priorto delivery of user device 704 to a carrier, prior to delivery of userdevice 704 to a user, etc.).

At 744, a carrier network (on which user device 704 is to be used) maybe selected at user device 704. At 746, responsive to selection of thecarrier network, a configuration package for the selected carriernetwork may be obtained by user device 704 from storage.

At 748, a request for activation may be generated at user device 704 andprovided to computer system 702. At 750, responsive to obtaining theactivation request, authorization for the activation may be verified atcomputer system 702.

At 752, if the authorization for the activation is verified, user device704 may be activated on the carrier side at computer system 702. At 754,the configuration package (for the selected carrier network) may beinstalled at user device 704 (e.g., prior to, in parallel with, or afterthe generation of the activation request). At 756, a notification of theactivation on the carrier side may be generated at computer system 702and provided to user device 704.

At 758, post-configuration clean-up may be performed at user device 704.As an example, one or more of the configuration packages stored at userdevice 704 may be caused to be deleted from user device 704. In one usecase, for example, responsive to user device 704 being configured forthe selected carrier network, (i) the configuration package comprising aset of carrier-specific parameters for configuring user device 704 forthe selected carrier network, (ii) one or more other configurationpackages comprising one or more other set of carrier-specific parametersfor configuring user device 704 for one or more other carrier networks,or (iii) both may be deleted.

FIG. 7C shows a dataflow diagram related to facilitatingcarrier-specific configuration of a user device using a third partyaccess system, in accordance with one or more embodiments. In anembodiment, at 762, a carrier network (on which user device 704 is to beused) may be selected at user device 704. At 764, responsive toselection of the carrier network, a request for activation and/or for aconfiguration package may be generated at user device 704 and providedto third party access system 706.

At 766, access information for the selected network may be obtained atthird party access system 706 and utilized to provide (at 768) therequest for activation of user device 704 and/or for a configurationpackage for user device 704 to computer system 702 (at the selectedcarrier network). As an example, the obtained access information maycomprise a username, a password, an access token, a network identifierfor an access point (on the selected carrier network for activating userdevices or obtaining configuration information), a network addressassociated with such access point, or other information.

At 770, responsive to obtaining the activation/configuration request,authorization for the activation and/or the configuration package may beverified at computer system 702.

At 772, 774, and 776, if the authorization for the activation and/or theconfiguration package is verified, the configuration package may beobtained at computer system 702 and provided to third party accesssystem 706, the configuration package may be obtained at third partyaccess system 706 and provided to user device 704, and user device 704may be activated on the carrier side at computer system 702. At 778,responsive to obtaining the configuration package, the configurationpackage may be installed at user device 704. At 780 and 782, anotification of the activation on the carrier side may be generated atcomputer system 702 and provided to third party access system 706, andthe notification may be obtained at third party access system 706 andprovided to user device 704.

At 784, post-configuration clean-up may be performed at user device 704.For example, one or more post-configuration clean-up operationsdescribed herein or other operations may be performed.

In some embodiments, the various computers and subsystems illustrated inFIG. 1 may comprise one or more computing devices that are programmed toperform the functions described herein. The computing devices mayinclude one or more electronic storages (e.g., carrier access database132, configuration database 134, or other electric storages), one ormore physical processors programmed with one or more computer programinstructions, and/or other components. The computing devices may includecommunication lines or ports to enable the exchange of information witha network (e.g., network 150) or other computing platforms via wired orwireless techniques (e.g., Ethernet, fiber optics, coaxial cable, WiFi,Bluetooth, near field communication, or other technologies). Thecomputing devices may include a plurality of hardware, software, and/orfirmware components operating together to provide the functionalityattributed herein to the servers. For example, the computing devices maybe implemented by a cloud of computing platforms operating together asthe computing devices.

The electronic storages may comprise non-transitory storage media thatelectronically stores information. The electronic storage media of theelectronic storages may include one or both of system storage that isprovided integrally (e.g., substantially non-removable) with the serversor removable storage that is removably connectable to the servers via,for example, a port (e.g., a USB port, a firewire port, etc.) or a drive(e.g., a disk drive, etc.). The electronic storages may include one ormore of optically readable storage media (e.g., optical disks, etc.),magnetically readable storage media (e.g., magnetic tape, magnetic harddrive, floppy drive, etc.), electrical charge-based storage media (e.g.,EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.),and/or other electronically readable storage media. The electronicstorages may include one or more virtual storage resources (e.g., cloudstorage, a virtual private network, and/or other virtual storageresources). The electronic storage may store software algorithms,information determined by the processors, information received from theservers, information received from client computing platforms, or otherinformation that enables the servers to function as described herein.

The processors may be programmed to provide information processingcapabilities in the servers. As such, the processors may include one ormore of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. In some embodiments, the processors may includea plurality of processing units. These processing units may bephysically located within the same device, or the processors mayrepresent processing functionality of a plurality of devices operatingin coordination. The processors may be programmed to execute computerprogram instructions to perform functions described herein of subsystems112-118, subsystems 202-208, or other subsystems. The processors may beprogrammed to execute computer program instructions by software;hardware; firmware; some combination of software, hardware, or firmware;and/or other mechanisms for configuring processing capabilities on theprocessors.

It should be appreciated that the description of the functionalityprovided by the different subsystems 112-118 or 202-208 described hereinis for illustrative purposes, and is not intended to be limiting, as anyof subsystems 112-118 or 202-208 may provide more or less functionalitythan is described. For example, one or more of subsystems 112-118 or202-208 may be eliminated, and some or all of its functionality may beprovided by other ones of subsystems 112-118 or 202-208. As anotherexample, additional subsystems may be programmed to perform some or allof the functionality attributed herein to one of subsystems 112-118 or202-208.

Although the present invention has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred embodiments, it is to be understood thatsuch detail is solely for that purpose and that the invention is notlimited to the disclosed embodiments, but, on the contrary, is intendedto cover modifications and equivalent arrangements that are within thescope of the appended claims. For example, it is to be understood thatthe present invention contemplates that, to the extent possible, one ormore features of any embodiment can be combined with one or morefeatures of any other embodiment.

What is claimed is:
 1. A system for facilitating carrier-specificconfiguration of user devices, the system comprising a user device thatincludes one or more physical processors programmed to execute computerprogram instructions which, when executed, cause the user device to:store configuration packages comprising sets of carrier-specificparameters for configuring the user device for carrier networks ofdifferent carriers; select one of the carrier networks on which the userdevice is to be configured to operate; responsive to the selection ofthe carrier network, determine whether the stored configuration packagescomprise a configuration package that comprises one or morecarrier-specific parameters for configuring the user device for theselected carrier network; responsive to the determination that thestored configuration packages do not comprise the configuration packagethat comprises the one or more carrier-specific parameters forconfiguring the user device for the selected carrier network, provide,to a carrier-side computer system on the selected carrier network, alimited access request to the selected carrier network; and responsiveto limited access being granted by the carrier-side computer systembased on the limited access request, provide, to the carrier-sidecomputer system, a configuration request for configuring the user devicefor the selected carrier network, wherein the configuration requestcomprises a location of the user device.
 2. The system of claim 1,further comprising: responsive to the configuration request, obtain,from the carrier-side computer system, a first configuration packagethat comprises a set of one or more carrier-specific parameters forconfiguring the user device for the selected carrier network, the firstconfiguration package being selected based on the location of the userdevice.
 3. The system of from 2, further comprising: select a subset ofone or more carrier carrier-specific parameters from the set of one ormore carrier-specific parameters based on the location of the userdevice; and responsive to the selection of the subset of one or morecarrier carrier-specific parameters, cause the user device to beconfigured using the selected subset of one or more carriercarrier-specific parameters.
 4. The system of claim 2, furthercomprising: responsive to configuring the user device for further accessto the selected network carrier, cause the first configuration packagethat comprises the set of one or more carrier-specific parameters forconfiguring the user device for the selected carrier network to bedeleted from the user device.
 5. The system of claim 2, furthercomprising: select a subset of one or more carrier carrier-specificparameters from the set of the one or more carrier-specific parametersthat are supported by the user device to be used to configure the userdevice; and responsive to the selection of the subset of one or morecarrier carrier-specific parameters, cause the user device to beconfigured using the selected subset of one or more carriercarrier-specific parameters such that one or more other subsets of oneor more carrier carrier-specific parameters that are not supported bythe user device are not used to configure the user device.
 6. The systemof claim 1, wherein the limited access request comprises amulti-carrier-recognized access point name that is recognized by thecarrier networks of the different carriers for obtainingcarrier-specific parameters for configuring the user device via thecarrier networks of the different carriers.
 7. The system of claim 1,further comprising: responsive to configuring the user device forfurther access to the selected network carrier, provide an activationrequest to the carrier-side computer system on the selected carriernetwork, wherein the activation request comprises at least one of anidentifier for the user device or an identifier for a smart card in theuser device.
 8. The system of claim 1, further comprising: responsive toconfiguring the user device for further access to the selected networkcarrier, cause one or more of the stored configuration packages that donot comprise the one or more carrier-specific parameters for configuringthe user device for the selected carrier network to be deleted from theuser device.
 9. The system of claim 1, wherein the user device storesthe configuration packages in a memory of the user device.
 10. Thesystem of claim 1, wherein the stored configuration packages arepre-stored by a manufacturer of the user device, and wherein the storedconfiguration packages are pre-stored by the manufacturer of the userdevice during a manufacturing process, prior to a delivery of the userdevice to a carrier, or prior to delivery of the user device to a user.11. A method of facilitating carrier-specific configuration of userdevices, the method being implemented by a user device that includes oneor more physical processors programmed to execute computer programinstructions which, when executed, perform the method: storingconfiguration packages comprising sets of carrier-specific parametersfor configuring the user device for carrier networks of differentcarriers; selecting one of the carrier networks on which the user deviceis to be configured to operate; responsive to the selection of thecarrier network, determining whether the stored configuration packagescomprise a configuration package that comprises one or morecarrier-specific parameters for configuring the user device for theselected carrier network; responsive to the determination that thestored configuration packages do not comprise the configuration packagethat comprises the one or more carrier-specific parameters forconfiguring the user device for the selected carrier network, providing,to a carrier-side computer system on the selected carrier network, alimited access request to the selected carrier network; and responsiveto limited access being granted by the carrier-side computer systembased on the limited access request, providing, to the carrier-sidecomputer system, a configuration request for configuring the user devicefor the selected carrier network, wherein the configuration requestcomprises a location of the user device.
 12. The method of claim 11,further comprising: responsive to the configuration request, obtaining,from the carrier-side computer system, a first configuration packagethat comprises a set of one or more carrier-specific parameters forconfiguring the user device for the selected carrier network, the firstconfiguration package being selected based on the location of the userdevice.
 13. The method of from 12, further comprising: selecting asubset of one or more carrier carrier-specific parameters from the setof one or more carrier-specific parameters based on the location of theuser device; and responsive to the selection of the subset of one ormore carrier carrier-specific parameters, causing the user device to beconfigured using the selected subset of one or more carriercarrier-specific parameters.
 14. The method of claim 12, furthercomprising: responsive to configuring the user device for further accessto the selected network carrier, causing the first configuration packagethat comprises the set of one or more carrier-specific parameters forconfiguring the user device for the selected carrier network to bedeleted from the user device.
 15. The method of claim 12, furthercomprising: selecting a subset of one or more carrier carrier-specificparameters from the set of the one or more carrier-specific parametersthat are supported by the user device to be used to configure the userdevice; and responsive to the selection of the subset of one or morecarrier carrier-specific parameters, causing the user device to beconfigured using the selected subset of one or more carriercarrier-specific parameters such that one or more other subsets of oneor more carrier carrier-specific parameters that are not supported bythe user device are not used to configure the user device.
 16. Themethod of claim 11, wherein the limited access request comprises amulti-carrier-recognized access point name that is recognized by thecarrier networks of the different carriers for obtainingcarrier-specific parameters for configuring the user device via thecarrier networks of the different carriers.
 17. The method of claim 11,further comprising: responsive to configuring the user device forfurther access to the selected network carrier, providing an activationrequest to the carrier-side computer system on the selected carriernetwork, wherein the activation request comprises at least one of anidentifier for the user device or an identifier for a smart card in theuser device.
 18. The method of claim 11, further comprising: responsiveto configuring the user device for further access to the selectednetwork carrier, causing one or more of the stored configurationpackages that do not comprise the one or more carrier-specificparameters for configuring the user device for the selected carriernetwork to be deleted from the user device.
 19. The method of claim 11,wherein the user device stores the configuration packages in a memory ofthe user device.
 20. The method of claim 11, wherein the storedconfiguration packages are pre-stored by a manufacturer of the userdevice, and wherein the stored configuration packages are pre-stored bythe manufacturer of the user device during a manufacturing process,prior to a delivery of the user device to a carrier, or prior todelivery of the user device to a user.